Viewing a Job Log File
When a job runs, ePublisher AutoMap creates a log file that documents the steps performed for that job. You can view this log file when one exists. ePublisher AutoMap keeps the log file only for the last time the job ran. Previous log files are not kept. A composition job writes its own log beside its job file in the same way, so View Log opens the record of the last composition.
To view a log file
Start ePublisher AutoMap.
Select the job to view the log for in the ePublisher AutoMap main window.
On the Job menu, click View Log.
Finding Warnings and Errors in a Log
Job logs and composition logs mark the lines that need your attention. A warning line begins with [WARN] and an error line begins with [ERROR], which is the same convention the per-target generate.log file has always used. On a console set to a language other than English, these markers appear translated.
The count in the closing summary matches the marked lines, so a log that ends with 2 warning(s), 0 error(s) reported. contains exactly two lines marked [WARN]. Informational lines are not marked. A composition job closes with a summary of the same shape that also reports how many groups it composed.
A composition job relays the output of each member it builds into its own log, so a member's warnings and errors are visible where you are already reading. Those relayed lines belong to the member's own log and its own count — the composition does not add them to its summary. When a relayed warning needs attention, open that member's log to see it in context.
If a log has less step-by-step detail than you expect, check whether the job's Verbose logging option is cleared, or whether the run passed -q. For more information, see Setting Build Options for a Job.
When a Job Target Is Missing from the Stationery
A job names the targets it builds, but the Stationery defines what those targets are: the job customizes how a target builds, while the Stationery defines what exists. If a job names a target the Stationery no longer defines, the run stops with an error naming both the target and the Stationery.
That error is telling you the job and its Stationery have drifted apart — usually because a target was renamed or removed in the Stationery after the job was written. Resolve it by resaving the Stationery with that target, or by removing or renaming the target in the job so the two agree, and then run the job again.
Note: This is a change in behavior. Previously, ePublisher AutoMap silently recreated the missing target using the output format's default settings. The job kept producing output, but that output was configured with format defaults rather than the settings the Stationery author intended, and nothing indicated the substitution.